View TSS463-AA_711630.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

rev. 4205a?auto?03/03 features fully compliant to van specification iso/11519-3 handles all specified module types handles all specified message types handles retransmission of frames on contention and errors 3 separate line inputs with automatic diagnosis and selection normal or pulsed (optical and radio mode) coding van transfer rate: 1 mbit/s maximum spi/sci interface ? spi transfer rate: 4 mbit/s maximum ? sci transfer rate: 125 kbit/s maximum idle and sleep modes 128 bytes of general-purpose ram 14 identifier registers with all bits individually maskable 6-source maskable interrupt, including an interrupt-on-reset to detect glitches on the reset pin integrated crystal or resonator oscillator with internal baud rate generator and buffered clock output single +5v power supply 0.8 m cmos technology so16 package description the tss463aa is a circuit that allows the transfer of all the status information needed in a car or truck over a single low-cost wire pair, that minimizes electrical wire usage. it can be used to interconnect powerful functions to control and interface car body elec- tronics (lights, wipers, power window, etc.). the tss463aa is fully compliant with the van iso standard 11519-3. this standard supports a wide range of applications such as low-cost remote-controlled switches. typically it is used for lamp control, complex, highly-autonomous, distributed systems, which require fast and secure data transfers. the tss463aa is a microprocessor-interfaced line controller for mid- to high-com- plexity bus-masters and listeners like dashboard controllers, car stereo or mobile telephone cpus. the microprocessor interface consists of a 256-byte ram and a register area divided into 11 control registers, 14 channel register sets and 128 bytes of general purpose ram, used as a message storage area, and a 6-source maskable interrupt. the circuit operates in the ram using dma techniques, controlled by the channel and control registers. this allows virtually any microprocessor, including spi/sci interface, to be connected easily to the tss463aa. messages are encoded in enhanced manchester code, and an optional pulsed code for use with an optical or radio link, at a maximum bit rate of 1 mbit/s. the tss463aa analyzes the messages received or transmitted according to 6 different criteria includ- ing some higher level checks. in addition, the bus interface has three separate inputs with automatic source diagno- sis and selection. the interface allows for multibus listening or the automatic selection of the most reliable source at any time if several line receivers are connected to the same bus. van data link controller with serial interface TSS463-AA
2 TSS463-AA 4205a ? auto ? 03/03 block diagram
3 TSS463-AA 4205a ? auto ? 03/03 pin configuration pin description 1 16 215 314 413 512 6 11 710 8 9 miso ss int reset vdd xtal1 xtal2 test/vss ckout mosi sclk gnd txd rxd0 rxd2 rxd1 top view i/o type pin name pin no. pin function o 3-state miso 1 spi/sci data output i trigger cmos ss 2 spi/sci slave select (active low) open-drain int 3 interrupt (active low) power vdd 4 + 5v power supply i cmos xtal1 5 crystal oscillator or clock input pin from 1 to 16 mhz o xtal2 6 crystal oscillator output pin ground test/vss 7 test mode input o ckout 8 buffered clock output i cmos pull-down rxd1 9 van bus input 1 i cmos pull-down rxd2 10 van bus input 2 i cmos pull-down rxd0 11 van bus input 0 o 3-state txd 12 van bus output ground gnd 13 i trigger cmos pull-up reset 14 hardware reset (active low) i trigger cmos sclk 15 spi/sci clock input i trigger cmos mosi 16 spi/sci data input
4 TSS463-AA 4205a ? auto ? 03/03 application the tss463aa is a microprocessor controlled line controller for the van bus. it can interface to virtually any microprocessor which includes spi or sci interface. the tss463aa provides one full motorola compatible spi interface. it includes one full compatible intel uart (mode 0 only). and finally, one 9-bits sci interface is also integrated. in addition, the circuit features a single interrupt pin. this pin can be treated as level sensitive. for example, if there is a pending interrupt inside the circuit when another interrupt is reset, the int pin will emit a high pulse with the same pulse width as the internal write strobe (typically 20 ns). figure 1. typical application with motorola spi mode notes: 1. the tss463aa reset pin can either be connected to gnd through a 1 f capaci- tor, or the c reset pin or unconnected (inactive with internal pull-up). 2. leaving miso output pin floating in high impedance mode slightly increases standby consumption. a 100 k ? pull-up/pull-down resistor is recommended. test/vss txd mc ckout irq port x.y miso xtal1 int ss reset (1) miso 1 2 3 4 5 6 7 89 10 11 12 13 14 15 16 sclk mosi rxd0 rxd1 rxd2 reset (1) vdd gnd xtal2 van bus general i/o remaining pins sclk (if needed) 100k mosi ckout tss463 microcontroller
5 TSS463-AA 4205a ? auto ? 03/03 microprocessor interface the processor controls the tss463aa by reading and writing the internal registers of the circuit. these registers appear to the processor as regular memory locations. interface modes the tss463aa must be connected with an spi or sci serial interface. the following section provides information on switching from one mode to another. motorola spi mode the first two bytes to be sent by the master (cpu) are called ? initialization sequence ? : this sequence provides a proper asynchronous reset in the tss463aa and it selects the motorola spi, intel spi or the sci serial mode. this initialization sequence is shown on figure 4. two 0x00 will cause an internal reset and assert the motorola spi mode, two ? 0xff ? will provide an internal reset and assert the intel ? spi mode and ? 9 bits to 0 followed by 0xff or 0xfe ? will generate an internal reset and assert the 9-bits sci mode. figure 2. mode configuration byte the motorola serial peripheral interface (spi) is fully compatible with the spi motorola protocol. the interface is implemented for slave-mode only (the tss463aa can not gen- erate spi frames by itself). the spi interface allows the interconnection of several cpus and peripherals on the same printed circuit board. the spi mode interface consists of 4 pins: separate wires are required for data and clock, so the clock is not included in the data stream as shown in figure 5. one pin is needed for the serial clock (sclk), two pins for data communication mosi and miso and one pin for slave select (ss ). mosi or mosi 0 . 0000 . 0000 0x00 sclk ss ss sclk spi 8 pulses sci 9 pulses 0x00 1 . 1111 . 1111 internal reset and spi mode (intel or motorola) internal reset and sci mode 0xff 0xff intel motorola internal reset internal reset
6 TSS463-AA 4205a ? auto ? 03/03 figure 3. spi data stream sclk: serial clock the master device provides the serial clock for the slave devices. data is transferred synchronously with this clock in both directions. the master and the slave devices send/receive a data byte during an eight-clock pulse sequence. mosi: master out slave in the mosi pin is the master device data output (cpu) and the slave device data input (tss463aa). data is transferred serially from the master to the slave on this line; most significant bit (msb) first, least significant bit (lsb) last. miso: master in slave out the miso pin is configured as the slave device data output (tss463aa) and as master device data input (cpu). when the slave device is not selected (ss = 1), this pin is in high impedance state. ss : slave select the ss pin is the slave chip select. it is low active. a low state on the slave select input allows the tss463aa to accept data on the mosi pin and send data on the miso pin. the slave select signal must not toggle between each transmitted byte and should be left at a low level during the whole spi frame. ss must be asserted to inactive high level at the end of the spi frame. as mentioned before, if ss is not asserted, miso pin is in a high impedance state and incoming data is not driven to the serial data register. spi protocol the general format of the data communication in the spi frame between the tss463aa and the host is a bit-for-bit exchange on each sclk clock pulse. data is arranged in the tss463aa such that the significance of a bit is determined by its position from the start for output and from the end for input, most significant bit (msb) is sent first. bit exchanges in multiples of 8 bits are allowed. the idle clock polarity (cpol) and the clock phase (cpha) are not programmable: the cpol and cpha values to be programmed in the master (cpu) are cpol = cpha = 1. this is available for all modes. waveforms with transmit and sample points are shown in figure 6. 0x55 sclk mosi ss spi 8 pulses 0x66 miso
7 TSS463-AA 4205a ? auto ? 03/03 figure 4. cpol and cpha in the tss463aa at the beginning of a transmission over the serial interface, the first byte is the address of the tss463aa register to be accessed. the next byte transmitted is the control byte which determines the direction of the communication. the following bytes are data bytes (consecutive bytes are written in or read from address, address + 1, address + 2,..., address + n with n = 0 to 28). to make sure the tss463aa is not out of synchronization, the spi interface will trans- mit data ? 0xaa" and "0x55 ? on the miso pin during address and control byte time. this way, the master always ensures the tss463aa is well-synchronized. if the tss463aa is out of synchronization, the master can assert the ss pin inactive to re synchronize the spi interface or can assert the reset pin active or can send an initialization sequence. when the ss pin is inactive, the sclk is allowed to toggle. this will have no effect on the tss463aa spi module. spi control byte the spi control byte is transmitted by the master (cpu) to the tss463aa. it specifies whether it is a tss463aa write or read. table 1. spi control byte dir: serial transfer direction zero : read operation. the data bytes will be read by the master (cpu) from the tss463aa. one : write operation. the data bytes will be written by the master (cpu) to the tss463aa. in both cases, address auto-increment mechanism will take place when more than one data byte is read or written. this mechanism is inhibited when address value reaches 0xff. the seven following bits are reserved and must be equal to: 1100000. when the master (cpu) conducts a write, it sends an address byte, a control byte and data bytes on its mosi line. the slave device (tss463aa) will send, if well-synchro- nized, ? 0xaa ? during the address byte and ? 0x55 ? during the control byte on its miso line. 0x55 sclk mosi ss spi 8 pulses data t ransmit points data sample points cpol = cpha = 1 miso 0x66 7 6 5 4 3 2 1 0 dir 1 1 0 0 0 0 0
8 TSS463-AA 4205a ? auto ? 03/03 when the master (cpu) conducts a read, it sends an address byte, a control byte and dummy characters ("0xff" for instance) on its mosi line. in the case of a van mes- sages ram read (van frame received), the first data byte sent back by the tss463aa on its miso pin is the data length so the master knows how many dummy characters it must send to read the van frame properly. when the tss463aa responds back with data, it will not take care of the mosi line. the master must activate and de-activate ss between each data frame. synchronization bytes must be monitored carefully. for instance, if ? 0xaa ? and ? 0x55 ? are not monitored correctly, then the previous transmission may be incorrect too. a control byte containing "0x00" or "0xff" is forbidden except during an "initialization sequence". intel spi mode the intel spi mode is the second type of interface. as mentioned before, the tss463aa enters this mode if the initialization sequence contains (first two bytes received) "0xff, 0xff". this mode is fully compatible to the intel uart serial interface programmed in mode 0 only. it is the same as motorola spi mode (same cpol and cpha) but with inverted communication sense (lsb first and msb last). the protocol is also the same. however, from the master point of view (host microcontroller), the hardware is different. figure 5 shows how to connect the tss463aa and intel type microcontroller. figure 5. typical application with the 8051 uart in mode 0 notes: 1. the reset pin can either be connected to gnd through a 1 f capacitor, or the microcontroller reset pin or unconnected (inactive with internal pull-up). int irq port x.z ss port x.y rxd 1 2 3 4 5 6 7 89 10 11 12 13 14 15 sclk miso mosi rxd0 rxd1 rxd2 txd reset (1) vdd gnd ckout xtal1 xtal2 txd van bus general i/o remaining pins test/vss xtal1 c1 c2 100k (if needed) optional reset (1) 16 microcontroller tss463
9 TSS463-AA 4205a ? auto ? 03/03 the master device provides the serial clock on the txd pin and is still connected to sclk pin of the slave device. then, the rxd replaces the mosi and miso pins and is a bi-directional pin. to achieve a correct communication, the user should add a few gates to connect the master rxd pin to the mosi-miso slave pins. figure 5 proposes two 3-state buffers controlled by the master through a general pur- pose i/o pin. it is obvious that, in this intel spi mode, the master cannot monitor the "0xaa and 0x55" synchronization bytes while sending the address and control bytes. it is the only excep- tion in this mode compared with the motorola spi mode. sci mode the sci mode is the third type of interface. the tss463aa enters this mode if the ini- tialization sequence contains (first two bytes received) "0x00, 0xff". the sci is compatible with a 9-bits sci protocol. the interface is implemented for slave- mode only (the tss463aa cannot generate sci frames by itself). the sci interface allows an interconnection of several cpus and peripherals on the same printed circuit board. the sci mode interface consists of 4 pins: separate wires are required for data and clock, so the clock is not included in the data stream as shown in figure 6. one pin is needed for the serial clock (sclk), two pins for data exchange mosi and miso and one pin for slave select ss . figure 6. sci data stream sclk: serial clock the master device provides the serial clock for the slave devices. data is transferred synchronously with this clock in both directions. the master and the slave devices exchange a data byte during a nine clock pulses sequence. however, the tss463aa will only monitor 8 bits on its mosi line and send 9 bits on its miso line. mosi: master out slave in the mosi pin is the master device data output (cpu) and the slave device data input (tss463aa). data is transferred serially from the master to the slave on this line; least significant bit (lsb) first, most significant bit (msb) last. the tss463aa will only moni- tor 8 bits starting from the lsb to msb-1. miso: master in slave out the miso pin is configured as the slave device data output (tss463aa) and as master device data input (cpu). when the slave device is not selected (ss = 1), this pin is in high impedance state. the value of the msb (9 th bit) sent on the miso pin will always be "1" and should not be used by the master. ss : slave select the ss pin is the slave chip select. it is low active. a low state on the slave select input allows the tss463aa to accept data on the mosi pin and send data on the miso pin. mosi miso 0x55 ss sclk sci 9 pulses 0x66
10 TSS463-AA 4205a ? auto ? 03/03 the slave select signal must not toggle between each transmitted byte and therefore, should be left at a low level during the whole sci frame. ss must be asserted to inactive high level at the end of the sci frame. if ss is not asserted, miso pin is in high impedance state and incoming data is not driven to the serial data register. sci protocol same as the spi protocol described earlier except for data arranging (lsb first and msb last). only 8 bits are monitored by the tss463aa and master must monitor the 8 first bits too (9 th bit always equal to 1). sci control byte same as the spi control byte. clocks and speed considerations sclk and xtal clocks the spi/sci speed rate is given by the cpu producing sclk. xtal clock controls the speed rate on the van bus. the two clocks are asynchronous, but a minimum spi/sci interframe spacing must be apply according to xtal clock. intel and motorola spi modes within an spi byte, the maximum speed allowed on the mosi line is 4 mbits/s. for example, when using a 1 mhz oscillator (sufficient to provide 62.5 kts/s on the van bus) the minimum inter-character delay is 12 s (12 oscillator periods). speed consider- ations are detailed in figure 7. figure 7. spi speed considerations sci mode within an sci 9-bits data, the maximum speed allowed on the mosi line is 125 kbits/s. when using a 1 mhz oscillator, the data transfer speed and the minimum delay time between sci bytes are shown on figure 8. ss s at 1 mhz) (4 s at 1 mhz) (15 s at 1 mhz) 12 xtal min 8 xtal min 15 xtal min 4 xtal min mosi address control sclk 4 mbits/s max for sclk data (12 s at 1 mhz) (8
11 TSS463-AA 4205a ? auto ? 03/03 figure 8. sci speed considerations interrupts if an event occurs in the tss463aa that needs the attention of the processor, this will be signalled on the active low, open-drain interrupt request pin. the event that creates this request is controlled by the internal registers. every time the microprocessor accesses any of the interrupt registers (addresses 0x08 to 0x0b), the int pin will be released momentarily. this enables the tss463aa to work with processors that have either edge or level sensitive interrupt inputs. reset the reset is applied asynchronously or synchronously to the xtal clock. asynchronous reset it can be done either by the reset pin (hardware asynchronous reset) or by software (software asynchronous reset). the reset pin is a cmos trigger input with a pull-up resistor (~ 70 k ? ). an external 1 f capacitor to gnd provides to reset pin an efficient behavior. the asynchronous software reset is made by the "initialization sequence" described in ? motorola spi mode ? on page 5. two "0x00" bytes provide an asynchronous software reset and configure the tss463aa in the motorola spi mode while two "0xff" bytes provide a reset and configure the com- ponent in the intel spi mode and "0x00 followed by 0xff " provide a reset and configure the component in the sci mode. the ss pin must be asserted as shown on figure 9. the spi/sci logic will monitor these two bytes and provide an internal reset pulse asserting the tss463aa in the right mode. synchronous reset a synchronous reset (regarding xtal clock) is available on the tss463aa during cur- rent operation. it is made through the gres command bit of the command register (address 0x03). the two kinds of reset are ordered and filtered. then the internal reset, always asserted asynchronously, enables the internal oscillator. then it waits for 12 clock periods and the oscillator stability. the different blocks of the tss463aa need to be turned on synchronously. the release of the internal reset is synchronous and a loose of clock can let the tss463aa in per- manent reset after applying reset. it is important to note that even after a reset on the reset pin, the user should wait for 12 clock periods before sending the "initialization sequence" in order to select the spi or sci mode (because the default mode after a hardware reset is the motorola spi mode). data control address 12 xtal min (8 s at 1 mhz) (4 s at 1 mhz) 15 xtal min (15 s at 1 mhz) ss sclk mosi start bit stop bit 125 kbits/s max for sclk 8 xtal min 4 xtal min (12 s at 1 mhz)
12 TSS463-AA 4205a ? auto ? 03/03 figure 9. asynchronous software reset with uart intel mode oscillator an oscillator is integrated in the tss463aa, and consists of an inverting amplifier of which the input is xtal1 and the output xtal2. a parallel resonance quartz crystal or ceramic resonator must be connected to these pins. as shown in figure 5, two capacitors have to be connected from the crystal pins to ground. the values of c2 depend on the frequency chosen and can be selected using the schematic given in figure 39. if the oscillator is not used, then a clock signal must be fed to the circuit via the xtal1 input. note that this pin will behave as a cmos level compatible schmitt trigger input. in this case the xtal2 output should be left unconnected. the oscillator also features a buffered clock output pin ckout. the signal on this pin is directly buffered from the xtal1 input, without inversion. there is one more pin used for the oscillator. the test/vss pin is in fact its ground, and unless this pin is firmly connected to ground, with decoupling capacitors, the oscilla- tor will not operate correctly. the test mode itself, i.e., when the test/vss pin is held high, is only intended for fac- tory use, and the functionality of this mode is not specified in any way. the test/vss pin is subject to change without notice, the only exception is for incom- ing inspection tests using the test program. the clock signal is then fed to the clock generator that generates all the necessary tim- ing signals for the operation of the circuit. the clock generator is controlled by a 4-bit code called the clock divider. sclk 15 xtal min mosi 0xff 0xff ss reset internal pulse detection of forbidden control end of chip select 4 xtal min ftsclk () fxtal 1 () n 16 -------------------------- =
13 TSS463-AA 4205a ? auto ? 03/03 table 2. clock divider clock divider divide by 8 mhz 6 mhz 4 mhz 2 mhz kts/s kbits/s kts/s kbits/s kts/s kbits/s kts/s kbits/s 0000 1 500 400 375 300 250 200 125 100 0001 2 250 200 187.50 150 125 100 62.50 50 0010 4 125 100 93.75 75 62.50 50 31.25 25 0011 8 62.5 50 46.875+ 37.5 31.25 25 15.625 12.5 0100 16 31.25 25 23.438 18.75 15.625 12.5 7.813 6.25 0101 32 15.625 12.5 11.718 9.375 7.813 6.25 3.906 3.125 0110 64 7.813 6.25 5.859 4.688 3.906 3.125 1.953 1.562 0111 128 3.906 3.125 500 400 1.953 1.562 166.666 133.333 1000 1.5 333.333 266.666 250 200 166.666 133.333 83.333 66.666 1001 3 166.666 133.333 125 100 83.333 66.666 41.666 33.333 1010 6 83.333 66.666 62.50 50 41.666 33.333 20.833 16.666 1011 12 41.666 33.333 31.25 25 20.833 16.666 10.416 8.333 1100 24 20.833 16.666 15.625 12.50 10.416 8.333 5.208 4.166 1101 48 10.416 8.333 7.813 6.25 5.208 4.166 2.604 2.083 1110 96 5.208 4.166 3.906 3.125 2.604 2.083 1.302 1.042 1111 192 2.604 2.083 1.953 1.5625 1.302 1.042 0.651 0.521
14 TSS463-AA 4205a ? auto ? 03/03 van protocol line interface there are three line inputs and one line output available on the tss463aa. which of the three inputs to use is either programmable by software or automatically selected by a diagnosis system. the diagnosis system continuously monitors the data received through the three inputs, and compares it with each other and the selected bitrate. it then chooses the most reli- able input according to the results. the data on the line is encoded according to the van standard iso/11519-3. this means that the tss463aa is using a two level signal having a recessive (1) and a dom- inant (0) state. furthermore, due to the simple medium used, all data transmitted on the bus is also received simultaneously. the van protocol is hence a csma/cd (carrier sense multiple access collision detec- tion) protocol, allowing for continuous bitwise arbitration of the bus, and non-destructive (for the higher priority messa ge) collision detection. figure 10. csma/cd arbritration in addition to the van specification there is also a pulsed coding of the dominant and recessive states. this mode is intended to be used with an optical or radio link. in this mode, the dominant state for the transmitter is a low pulse, (2x prescaled clocks at the beginning of the bit) and the recessive state is just a high level. when receiving in this mode, it is not the state of the signal itself which is decoded, but the edges. also, recep- tion is imposed on the rxd0 input, and the diagnosis system does not operate correctly. in addition, in this mode there is an internal loopback in the circuit since optical trans- ceivers are not able to receive the signal that they transmit. node a: txd node a loses the arbitration node a releases the bus node b wins the arbitration node c loses the arbitration node c releases the bus r d node b: txd r d node c: txd r d on bus: data r d arbitration field r: recessive level d: dominant level 1 2 3
15 TSS463-AA 4205a ? auto ? 03/03 in figure 11 the pulsed waveforms are shown. in figure 14 through figure 20 the low "timeslots" (i.e. blocks of 16 prescaled clocks) should be replaced by the dominant waveform showed in figure 11 if the correct representations for pulsed coding are to be seen. figure 11. state encoding van frame figure 12. van bus frame the van bus supports three different module (unit) types: 1. the autonomous module, which is a bus master. it can transmit start of frame (sof) sequences, it can initiate data transfers and can receive messages. 2. the synchronous access module. it cannot transmit sof sequences, but it can initiate data transfers and can receive messages. 3. the slave module, which can only transmit using an in-frame mechanism and can receive messages. figure 13. hierarchical access methods figure 12 shows a normal van bus frame. it is initiated with a start of frame (sof) sequence shown in figure 14. the sof can only be transmitted by an autonomous module. during the preamble, the tss463aa will synchronize its bit rate clock to the data received. sof identifier field command data field frame check sum eod ack eof ext rak r/w rtr sof id com data ack eof eod autonomous rank 0 id com data fcs ack eof eod synchronous rank 1 data fcs ack eof eod slave rank 16 rtr fcs
16 TSS463-AA 4205a ? auto ? 03/03 figure 14. framing sequences when the complete sof sequence has been transmitted or received, the circuit will start the transmission or reception of the identifier field. all data on the van bus, including the identifier and frame check sum (fcs), are transmitted using enhanced manchester code. in enhanced manchester code, three nrz bits are transmitted first followed by one manchester bit, then three more nrz bits followed by one manchester bit and so on. since the high state is recessive and the low state is dominant, the bus arbitration can be done. if a module wants access to the bus, it must first listen to the bus during one full end of frame (eof) and one full inter frame spacing (ifs) period to determine whether the bus is free or not (i.e. no dominant states received). figure 15. data encoding the ifs is defined to be a minimum of 64 prescaled clock periods. the tss463aa, accepts an ifs of zero prescaled clocks for the reception only of a sof sequence. once the bus has been determined as being free, the module must, if it is an autono- mous module, emit an sof sequence or, if it is a synchronous access module, wait until it detects a preamble sequence. at this point there could be several modules transmitting on the bus, and there is no possibility of knowing if this is the case or not. therefore, the first field in which arbitra- van bus sequence van bus sequence number of prescaled clocks preamble start of frame start sync end of data ack end of frame 0 16 32 48 64 80 96 112 128 144 160 176 192 van bus sequence van bus sequence van bus sequence number of prescaled clocks nrz 0 nrz 1 manchester 0 manchester 1 0 8 16 24 32
17 TSS463-AA 4205a ? auto ? 03/03 tion can be performed is the identifier field. since the logical zeroes on the bus are dominant, and all data is transmitted with the most significant bit (msb) first, the first module to transmit a logical zero on the bus will be the prioritized module, i.e. the mes- sage that is tagged with the lowest identifier will have priority over the other messages. it is possible that two messages transmitted on the bus will have the same identifier. the tss463aa, therefore, continues the arbitration of the bus throughout the whole frame. moreover, if the identifier in transmission has been programmed for reception as well, it transmits and receives messages simultaneously, right up until the frame check sequence (fcs). only then, if the tss463aa has transmitted the whole message, it discard the message received. arbitration loss in the fcs field is considered as a crc error during transmission. this feature is called full data field arbitration, and it enables the user to extend the iden- tifier. for instance it can be used to transmit the emitting modules address in the first bytes of the data field, thus enabling the identifier to specify the contents of the frame and the data field to specify the source of the information. the identifier field of the van bus frame is always 12 bits long, and it is always followed by the 4-bit command field: the first bit of the command is the extension bit (ext). this bit is defined by the user on transmission and is received and retained by the tss463aa. to conform with the standard it should be set to 1 (recessive) by the user, else the frame is ignored without any it generation. the second bit is the request acknowledge bit (rak). if this bit is a logical one, the receiving module must acknowledge the transfer with an in-frame acknowledgement in the ack field. if it is set to logical zero, then the ack field must contain an acknowledge absent sequence. the third bit is the read/write (r/w). this bit indicates the direction of the data in a frame. ? if set to zero, it is a "write" message, i.e., data transmitted by one module to be received by another module. ? if it is set to one, it implies a "read" message, i.e. a request that another module should transmit data to be received by the one that requested the data (reply request message). last in the command field is the remote transmission request bit (rtr). this bit is a logical zero if the frame contains data and a logical one if the frame does not contain data. in order to conform with the standard, a received frame includes the combination r/w. rtr = 01 is ignored without any it generation. all the bits in the command field are automatically handled by the tss463aa, so the user need not to be concerned for encoding and decoding of these bits. the command bits transmitted on the van bus are calculated from the current status of the active message. the data field comes after the command field. this is just a sequence of bytes transmit- ted msb first. in the van standard the maximum message length is set to 28 bytes, but the tss463aa handles messages up to 30 bytes. the next field is the fcs field. this field is a 15 bit crc checksum defined by the follow- ing generator polynomial g(x) of order 15: g(x)= x 15 + x 11 + x 10 + x 9 + x 8 + x 7 + x 4 + x 3 + x 2 + 1 the division is done with a rest initialized to 0x7fff, and an inversion of the crc bits is performed before transmission.
18 TSS463-AA 4205a ? auto ? 03/03 however, since the crc is calculated automatically from the identifier, command and data fields by the tss463aa, therefore, the user should not be concerned with the cir- cuit. when the frame check sequence has been transmitted, the transmitting module must transmit an end of data (eod) sequence, followed by the acknowledge field (ack) and the end of frame sequence (eof) to terminate the transfer. figure 16. acknowledge sequences frame examples the frames transmitted on the van bus are generated by several modules, each sup- plying different parts of the message. figure 17 through figure 20 show the four frame types specified in the van standard, and the module that is generating the different fields. the most straightforward frame is the normal data frame in figure 17. like all other frames, it is initiated with a sof sequence. this sequence is generated by a bus master (not shown in the figure). during this frame, there is basically only one module transmitting with the exception of the acknowledgement, generated by the receiving module if requested in the rak bit. the reply request frame with immediate reply in figure 18 is the only frame in which a slave module can transmit data by filling it into the appropriate field. the only difference for the frame on the bus is that the r/w bit has changed state com- pared to the normal frame. this is a highly interactive frame where a bus master generates the sof and the initia- tor generates the identifier, the three first bits of the command, and the acknowledge. the rtr bit, the data field, the frame check, the eod and the eof are all generated by the replying module. the reply request frame with deferred reply in figure 19 is basically the same frame as the reply request frame with immediate reply, but since the requested module does not generate the rtr bit the requesting module will continue with the frame check, the eod and the eof. during this frame, the requested module will only generate the acknowledge, and only if this was requested by the initiator through the rak bit. finally, the deferred reply frame in figure 20 which is sent when a module has prepared a reply for a reply request that has been received earlier. this frame very closely mimics the normal data frame with the exception is the r/w bit that has changed state. van bus sequence van bus sequence number of prescaled clocks positive acknowledge absent acknowledge 0 8 16 24 32
19 TSS463-AA 4205a ? auto ? 03/03 figure 17. normal data frame frame on bus transmitting frame on bus transmitting module crc crc crc crc sof sof sof sof identifier identifier identifier identifier data data data data eof eof eof eof module receiving module receiving module : positive from receiver because rak is recessive rak ext r/w rtr ack : recessive for acknowledge from transmitter : recessive from transmitter : dominant from transmitter : dominant from transmitter - (*) manchester bit with acknowledgment without acknowledgment : absent from transmitter and from receiver because rak is dominant rak ext r/w rtr ack : dominant for no acknowledge from transmitter : recessive from transmitter : dominant from transmitter : dominant from transmitter - (*) manchester bit ext rak r/w rtr (*) ext rak r/w rtr (*) ext rak r/w rtr (*) ext rak r/w rtr (*) eod ack ack eod ack eod ack eod ack
20 TSS463-AA 4205a ? auto ? 03/03 figure 18. reply request frame with immediate reply figure 19. reply request frame with deferred reply (*) sof identifier rtr frame module requested module requesting (*) crc crc sof identifier data data eof eof on bus : absent from requestee and positive from requestor because rak is recessive rak ext r/w rtr ack : recessive for acknowledge from requestor : recessive from requestor : recessive from requestor : recessive from requestor and dominant from requestee - (*) manchester bit ext rak r/w rtr (*) eod ack ack ext rak r/w rtr eod ack sof rtr identifier frame on bus requesting (*) crc crc sof identifier eof eof module requested module : absent from requestor and positive from requestee because rak is recessive rak ext r/w rtr ack : recessive for acknowledge from requestor : recessive from requestor : recessive from requestor : recessive from requestor - (*) manchester bit ext rak r/w eod ack eod ack ack rtr ext rak r/w (*)
21 TSS463-AA 4205a ? auto ? 03/03 figure 20. deferred reply frame frame on bus module replying crc crc sof sof identifier identifier data data eof eof receiving module : absent from replyer and positive from receiver because rak is recessive rak ext r/w rtr ack : recessive for acknowledge from replyer : recessive from replyer : recessive from replyer : dominant from replyer - (*) manchester bit ext rak r/w eod ack eod ack ack ext rak r/w (*) (*) rtr rtr
22 TSS463-AA 4205a ? auto ? 03/03 diagnosis system the purpose of the diagnosis system is to detect any short or open circuits on either the data or data lines and to permit, if it is possible, to carry the communications on the non-defective line. the diagnosis system is based on the assumption that three separate line receivers are connected to the van bus see figure 1: one of the line receivers is connected in differential mode, sensing both data and data signals, and is connected to the rxd0 input. the other two line receivers are operating in single wire mode and are sensing only one of the two van bus signals: ? the line receiver sensing data is connected to rxd1 ? the line receiver sensing data is connected to rxd2 the diagnosis system analyzes and compares the data sent over both van lines. so, the diagnosis system executes a digital filtering and transition analyses. in order to per- form its investigation, three internal signals are generated, ri ( return to idle) , sdc ( synchronous diagnosis clock) and tip ( transmission in progress ). one of four operating modes can be chosen to manage the results of the diagnosis system. diagnosis states if the diagnosis system finds a failure on any of the van bus signals, it changes from nominal to degraded mode, and connects the line receiver not coupled to the failing sig- nal to the reception logic. when the diagnosis system finds that the failing signal is working again, it returns to nominal mode and re-connects the differential line receiver to the reception logic. a major error occurs when both the van bus signals failed. figure 21. diagnosis states nominal degraded data degraded data major error - failure during the frame - default of transitions on the valid input between 2 consecutive sdc rising edges. - protocol fault -in specified selection mode, every ri pulse when an eof is detected or through an active sdc. -in automatic selection mode and sdc active, no failuresampled by 2 consecutive sdc rising edges. -general reset
23 TSS463-AA 4205a ? auto ? 03/03 status bits give permanent information on the diagnosis performed, whatever the pro- grammed operating mode. this is encoded over three bits: sa, sb and sc. sa and sb bits indicate the four possible states of the van bus. table 3. status bits: sa and sb sc: as soon as one of the three inputs (rxd2, rxd1, rxd0) differs from the others in the input comparison analysis performed by the diagnosis system, sc is set. the only way to reset this status bit is through the ri signal or a general reset. internal operations digital filtering if several spurious pulses occur during one bit, the diagnosis for defective conductor may occur. to avoid such errors, digital filters are implemented. filtering operation is based on sampling of the comparator output signals. a transition is taken into account only if it is observed over five samples (1/16 th of timeslot). transition analyses these analyses are continuously done on the effective edges on comparators after digi- tal filtering. asynchronous diagnosis the asynchronous diagnosis is done by comparing the number of edges on data and data . if four edges are detected on one input and no edges on the other during the same period, the second input is considered faulty and the diagnosis mode will change to one of the degraded modes. synchronous diagnosis the synchronous diagnosis counts the number of edges on the data input connected to the reception logic during one sdc period. if there are less than four edges during one sdc period, the diagnosis mode will change to the major error mode. sa sb communication 0 0 mode nominal fault no fault on van bus status differential communication on data and data 0 1 mode degraded on data fault fault on data status communication on data 1 0 mode degraded on data fault fault on data status communication on data 1 1 mode major error fault fault on data and data status no communication on data and data (attempt to communicate alternatively on data then data every sdc period)
24 TSS463-AA 4205a ? auto ? 03/03 transmission diagnosis the transmission compares rxd1 and rxd2 inputs (through the input comparators and the filters) with the data transmitted on txd output. at a time when the transmission logic generates a dominant - recessive transition, the inputs can give different values. taking into account the filtering delay, the bus line seen as dominant is assumed to be correct, the other one, recessive, is considered faulty. the diagnosis mode is changed to reflect that. protocol fault the protocol fault is detected by counting the number of consecutive dominant timeslots. if eight consecutive timeslots are dominant, the diagnosis mode will change to the major error mode. generation of internal signals ri signal (return to idle) this signal is used to return to nominal mode in the three specified selection modes (see ? diagnosis states ? on page 22 and ? programming modes ? on page 25). the ri signal is disabled in automatic selection mode. the ri signal is a pulse generated when an eof is detected. thus, at the end of each frame, regarding the diagnosis status bit sa, sb and sc, the user can make its own choice. sdc signal (synchronous diagnosis clock) this time base is used by diagnosis system in automatic selection mode (see section ? programming modes ? , page 25) when no event is recorded on the bus. the sdc is generated either by a special sdc divider connected to the timeslot clock, or can be performed manually. the sdc clock period must be long compared to the timeslot duration. a typical sdc period should be greater than the maximum frame length appearing on the van network. tip signal (transmission in progress) this signal must be enabled to allow the transmission diagnosis (see section ? transition analyses ? , page 23). the tip turns on synchronously with the beginning of the transmission: for asynchronous bus access, the beginning of sof; for synchronous bus access, the beginning of the identifier field; and for a request of in frame reply, the rtr bit of the command field. the tip turns off synchronously with the end of the transmission: after eof; after a losing of arbitration or a code violation detection; and for a requestor of in frame reply, when the arbitration is lost on rtr the bit. this signal is not generated when the transmission logic only sends an ack.
25 TSS463-AA 4205a ? auto ? 03/03 programming modes four programming modes determine how to use the three different inputs and the diag- nosis system. 3 specified selection modes 1 automatic selection mode table 4. programming modes ma mb operating mode 0 0 differential communication 0 1 degraded communication on rxd2 (data ) 1 0 degraded communication on rxd1 (data) 1 1 automatic selection according the diagnosis status
26 TSS463-AA 4205a ? auto ? 03/03 registers the tss463aa memory map consists of three different areas, the control and status registers, the channel registers and the message data (or mailbox). mapping figure 22. memory map notes: 1. all the non-specified addresses between 0x00 and 0x7f are considered as absent. 2. (r) means read-only register. (w) means write-only register. (r/w) means read/write register. 3. value after reset is found after register name. if no value is given, the register is not initialized at reset. 0x70 to 0x77 (r/w) reserved 0x7c and 0x7d reserved channel 9 0x58 to 0x5f (r/w) channel 10 0x60 to 0x67 (r/w) 0x17 (r/w) channel 2 0x20 to 0x27 (r/w) 0x10 (r/w) 0x28 to 0x2f (r/w) channel 5 0x78 (r/w) 0x79 (r/w) 0x7a (r/w) 0x7b (r/w) channel 13 0x78 to 0x7f (r/w) 0x38 to 0x3f (r/w) id_mask [11..4] id_tag [11..4] id_mask [3..0] 0x11 (r/w) 0x12 (r/w) 0x13 (r/w) 0x14 and 0x15 0x16 (r/w) line control (0x00) 0x01 (r/w) transmit control (0x02) 0x81 data byte 1 diagnosis control (0x00) command (0x00) line status (0bx01xxx00) transmit status (0x00) last message status (0x00) last error status (0x00) reserved interrupt status (0x80) interrupt enable (0x80) 0x00 (r/w) 0x02 (r/w) 0x03 (w) 0x04 (r) 0x05 (r) 0x06 (r) 0x07 (r) 0x08 0x09 (r) 0x0b (w) interrupt reset 0x0a (r/w) 0xff data byte 127 0x80 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x89 0x8a 0x8b 0x8c data byte 0 data byte 2 data byte 3 data byte 4 data byte 5 data byte 6 data byte 7 data byte 8 data byte 9 data byte 10 data byte 11 data byte 12 channel 4 channel 8 channel 6 channel 12 channel 1 channel 11 channel 7 reserved 0x10 to 0x17 (r/w) 0x30 to 0x37 (r/w) 0x50 to 0x57 (r/w) 0x40 to 0x47 (r/w) 0x18 to 0x1f (r/w) 0x68 to 0x6f (r/w) 0x48 to 0x4f (r/w) 0x0c to 0x0f register message id_tag [3..0] + com drak + message address message length + status reserved channel 0 registers channel 0 id_tag (lsb) + com id_tag (msb) drak + message address message length + status 0x7e (r/w) channel 13 registers id_mask [11..4] 0x7f (r/w) id_mask [3..0] id_mask [11..4] channel 3 channel 13 channel 2 0x17 (r/w)
27 TSS463-AA 4205a ? auto ? 03/03 control and status registers line control register (0x00) read/write register. default value after reset: 0 00 reserved: bit 2, this bit must not be set by the user; a 0 must always be written to this bit. cd[3:0]:clock divider they control the van bus rate through a baud rate generator according to the formula below: pc: pulsed code one : the tss463aa will transmit and receive data using the pulsed coding mode (i.e optical or radio link mode). the use of this mode implies communication via the rxd0 input and the non-functionality of the diagnosis system. zero : (default at reset). the tss463aa will transmit and receive data using the enhanced manchester code. (rxd0, rxd1, rxd2 used). ivtx: invert txd output ivrx: invert rxd inputs the user can invert the logical levels used on either the txd output or the rxd inputs in order to adapt to different line drivers and receivers. one : a one on either of these bits will invert the respective signals. zero : (default at reset). the tss463aa will set txd to recessive state in idle mode and consider the bus free (recessive states on rxd inputs). transmit control register (0x01) read/write register. default value after reset: 0x02 mr[3:0]: maximum retries these bits allow the user to control the amount of retries the circuit will perform if any errors occurred during transmission. 7 6 5 4 3 2 1 0 cd3 cd2 cd1 cd0 pc 0 ivtx ivrx ftsclk () fxtal 1 () n 16 -------------------------- = 7 6 5 4 3 2 1 0 mr3 mr2 mr1 mr0 ver2 ver1 ver0 mt
28 TSS463-AA 4205a ? auto ? 03/03 table 5. retries note: bus contention is not regarded as an error and an infinite number of transmission attempts will be performed if bus contention occurs continuously. ver[2:0] = 001 dlc version after reset. these bits must not be set by user. 001 must always be written to these bits. mt: module type the three different module types are supported (see ? van frame ? on page 15): one : the tss463aa is at once an autonomous module (rank 0), a synchronous access module (rank 1) or a slave module (rank 16). zero : the tss463aa is at once an synchronous access module (rank 1) or a slave module (rank 16). mr [3:0] max. # of retries max. # of transmissions 0000 0 1 0001 1 2 0010 2 3 0011 3 4 0100 4 5 0101 5 6 0110 6 7 0111 7 8 1000 8 9 1001 9 10 1010 10 11 1011 11 12 1100 12 13 1101 13 14 1110 14 15 1111 15 16
29 TSS463-AA 4205a ? auto ? 03/03 diagnosis control register (0x02) read/write register default value after reset: 0 00. the diagnosis is discussed in greater detail in the section ? diagnosis system ? on page 22. in its four high order bits, the user can program the sdc rate sdc [3:0] in its two medium order bits, the diagnosis system mode is controlled: m1, m0. in the two low order bits, the user controls if the sdc and tip are to be generated automatically etip, esdc. sdc [3:0]: sdc divider the input clock is the timeslot clock. table 6. system diagnosis clock divider 7 6 5 4 3 2 1 0 sdc3 sdc2 sdc1 sdc0 ma mb etip esdc sdc divider sdc [3:0] divide by 0000 64 0001 128 0010 256 0011 512 0100 1024 0101 2048 0110 4096 0111 8192 1000 16384 1001 32768 1010 65536 1011 131072 1100 262144 1101 524288 1110 1048576 1111 2097152 sdc calculation : (see ? sdc signal (synchronous diagnosis clock) ? on page 24). notes: 1. for each module, determine the largest interframe spacing, lifs (*). 2. for the whole network, get the maximum lifs, max-lifs . 3. sdc period > max-lifs. (*) ifs min. = 4 ts example: for van frame speed rate = 62,5 kts/s (1 ts = 16 s), sdc >100 ms => 100 ms / 16 s = 6250, divider chosen: 8192, sdc [3:0] = 0111.
30 TSS463-AA 4205a ? auto ? 03/03 ma, mb: operating mode command bits table 7. diagnosis system command bits etip: enable transmission in progress the transmission in progress (tip) tells the diagnosis system to enable transmission diagnosis. one : enable tip generation zero : disable tip generation. esdc: enable system diagnosis clock the synchronous diagnosis clock (sdc) controls the cycle time of the synchronous diagnosis. one : enable sdc divider. zero : disable sdc divider. command register (0x03) write only register. reserved: bit 1, 2 these bits must not be set by the user; a zero must always be written to these bit. if the circuit is operating at low bitrates there might be a considerable delay between the writing of this register and the performing of the actual command (worst case 6 timeslots). the user is therefore recommended to verify, by reading the line status register (0x04), that the commands have been performed. gres: general reset the reset circuit command bit performs, if set, exactly as if the external reset pin was asserted. this command bit has its own auto-reset circuitry. one : reset active zero : reset inactive sleep: sleep command (see section ? sleep command ? , page 52).if the user sets the sleep bit, the circuit will enter sleep mode. when the circuit is in sleep mode, all non-user registers are setup to minimize power consumption. read/write accesses to the tss463aa via the spi/sci interface are impossible, the oscillator is stopped. to exit from this mode the user must apply either an hardware reset (external reset pin) or an asynchronous software reset (via the spi/sci interface). one: sleep active zero: sleep inactive ma mb 0 0 forces the communication on rxd0 (differential) 0 1 forces the communication on rxd2 (data ) 1 0 forces the communication on rxd1 (data) 1 1 automatic selection 7 6 5 4 3 2 1 0 gres sleep idle acti rear 0 0 msdc
31 TSS463-AA 4205a ? auto ? 03/03 idle: idle command (see section ? idle and activate commands ? , page 52). if the user sets the idle bit, the circuit will enter idle mode. in idle mode the oscillator will operate, but the tss463aa will not transmit or receive anything on the bus, and the txd output will be in three state. one : idle active zero : idle inactive acti: activate command (see section ? idle and activate commands ? , page 52). the activate command will put the circuit in the active mode, i.e it will transmit and receive normally on the bus. when the circuit is in activate mode the txd three-state output is enabled. one : activate active zero : activate inactive rear: re-arbitrate command this command will, after the current attempt, reset the retry counter and re-arbitrate the messages to be transmitted in order to find the highest priority message to transmit. one: re-arbitrate active zero: re-arbitrate inactive msdc: manual system diagnosis clock rather than using the sdc divider described in section ? message data (string pointed by: message pointer register + 1) ? , page 44, the user can use the manual sdc com- mand to generate a sdc pulse for the diagnosis system. this msdc pulse should be high at least 2 timeslot clocks. line status register (0x04) read only register default value after reset: 0bx01xxx00. this register reports the operation mode of the tss463aa in the sleep an idle bits (command register located at address 0 03) as well as the diagnosis system status bits sa to sc discussed in the section ? diagnosis system ? on page 22. spg: sleeping idg: idling default mode at reset sa, sb and sc: diagnosis system status bits sa and sb diagnosis system status bits 7 6 5 4 3 2 1 0 x spg idg sc sb sa txg rxg sb sa communication indication 0 0 nominal mode, differential communication 0 1 degraded over data , fault on data 1 0 degraded over data, fault on data 1 1 major error, fault on data and data
32 TSS463-AA 4205a ? auto ? 03/03 sc: as soon as one of the three inputs (rxd2, rxd1, rxd0) differs from the others in the input comparison analysis performed by the diagnosis system, sc is set. the only ways to reset this status bits through the ri signal or a general reset. txg: transmitting if this status bit is active, it indicates that the tss463aa has chosen an identifier to transmit, and it will continue to make transmission attempt for this message until it suc- ceeds or the retry count is exceeded. rxg: receiving the receiving indicates that there is activity on the bus. note : for safe modification of active channel registers both bits should be inactive (except ? abort ? command). transmission status register (0x05) read only register. default value after reset: 0x00. the transmission status register contains the number of retries made up-to-date, according tothe table above, and the channel currently in transmission. nrt [3:0]: number of retries done in transmission. idt [3:0]: channel number currently in transmission. last message status register (0x06) read only register. default value after reset: 0x00. this register is basically the same as the transmission status register. it contains the last identifier number that was successfully transmitted, received or exceeded its retry count. if it was a successful transmission, the number of retries performed can be seen in this register as well. nrtr [3:0]: number of retries done successfully in transmission. in case of reception nrtr[3:0] is undefined. idtr [3:0]: channel number that was successfully transmitted, received or exceeded its retry count. 7 6 5 4 3 2 1 0 nrt3 nrt2 nrt1 nrt0 idt3 idt2 idt1 idt0 7 6 5 4 3 2 1 0 nrtr3 nrtr2 nrtr1 nrtr0 idtr3 idtr2 idtr1 idtr0
33 TSS463-AA 4205a ? auto ? 03/03 last error status register (0x07) read only register. default value after reset: 0 00. the last error status register contains the error code for the last transmission or reception attempt. it is updated after each attempt, i.e., several error codes can be reported during one single transmission (with several retries). boc: buffer occupied when one channel configured in ? reply request ? mode has its ? received ? bit set when it attempts to transmit its request. boc with the link capability between two channels sharing the same received buffer, is set when one channel has already set its ? received ? bit in its ? message length and status channel register ? and a receive is attempt on the other one. one : boc active zero : boc inactive bov: buffer overflow bov indicates that the buffer length setup in the channel status register was shorter than the number of bytes received plus 1, and thus, some data was lost. one : bov active zero : bov inactive fcse: framing check sequence error fcse indicates a mismatch between the fcs received and the fcs calculated one : fcse active zero: fcse inactive acke: acknowledge error acke indicates a physical violation or collision on ack field of the frame when the tss463aa is a producer. one : acke active zero : acke inactive 7 6 5 4 3 2 1 0 x boc bov x fcse acke cv fv
34 TSS463-AA 4205a ? auto ? 03/03 figure 23. acke status bit cv: code violation cv indicates: either a manchester code violation (2 identical ts on manchester bit), or a physical violation (transmitted bit ? dominant ? , received bit ? recessive ? ), on fields id, com, data and crc. or a physical violation or collision on field ? preamble ? and the ? recessive ? bit of the ? star sync ? field. one: cv active zero: cv inactive fv: frame violation fv indicates a physical violation or collision on ack field of the frame when the tss463aa is a consumer. one: fv active zero: fv inactive rak* = 1 *rak: bit of the frame command field acke = 0 acke = 1 acke = 1 acke = 1 acke = 0 acke = 1 acke = 1 acke = 1 eod field ack field eod field ack field expected received received received expected received received received dlc: producer rak = 0
35 TSS463-AA 4205a ? auto ? 03/03 figure 24. fv status bit interrupt status register (0x09) read only register. default value after reset: 1xx0 0000 rst: reset interrupt re indicates that the circuit has detected a valid reset command via the reset pin or the reset command bit gres. this interrupt cannot be disabled, since its enable bit is set when a reset is detected. one: status flag activated zero: no status flag. te: transmit error status flag (or exceeded retry) this flag is set only when the max number of transmission (1 + mr [3:0]) is reached with error of transmission. one: status flag activated zero: no status flag. figure 25. exceeded retry with mr[3..0] = 3 fv = 0 fv = 1 fv = 1 fv = 1 fv = 0 fv = 1 fv = 1 fv = 1 eod field ack field eod field ack field expected received received received expected received received received dlc: consumer 7 6 5 4 3 2 1 0 rst x x te tok re rok rnok 1st tx 2nd tx 3rd tx set te set cher set chtx
36 TSS463-AA 4205a ? auto ? 03/03 tok: transmit ok status flag one: status flag activated zero: no status flag. re: receive error status flag one: status flag activated zero: no status flag. rok: receive ?with rak (rak=1)? ok status flag one: status flag activated zero: no status flag. rnok: receive ?with no rak (rak=0)? ok status flag one: status flag activated zero: no status flag. interrupt enable register (0x0a) read/write register. default value reset: 1xx0 0000 note: on reset the reset interrupt enable bit is set to 1 instead of 0, as is the general rule. tee: transmit error enable one: it enabled. zero: it disabled. toke: transmission ok enable one: it enabled. zero: it disabled. ree: reception error enable one: it enabled. zero: it disabled. roke: reception ? with rak ? ok enable one: it enabled. zero: it disabled. rnoke: reception ? with no rak ? ok enable one: it enabled. zero: it disabled. interrupt reset register (0x0b): write only register. reserved bit: 5 and 6. this bit must not be set by user; a zero must always be written to this bit. 7 6 5 4 3 2 1 0 1 x x tee toke ree roke rnoke 7 6 5 4 3 2 1 0 rstr 0 0 ter tokr rer rokr rnokr
37 TSS463-AA 4205a ? auto ? 03/03 rstr: reset interrupt reset one: status flag reset. zero: status flag unchanged. ter: transmit error status flag reset one: status flag reset. zero: status flag unchanged. tokr: transmit ok status flag reset one: status flag reset. zero: status flag unchanged. rer: receive error status flag reset one: status flag reset. zero: status flag unchanged. rokr: receive ? with rak ? ok status flag reset one: status flag reset. zero: status flag unchanged. rnokr: receive ? with no rak ? ok status flag reset one: status flag reset. zero: status flag unchanged. figure 26. update of the status register rst te tok re rok rnok flag write flag write flag write flag write flag write int rstr tokr rer rokr rnokr ter toke ree roke rnoke tee interrupt status register interrupt enable register interrupt reset register pin 3 internal reset reset rxg, txg line status register (0x04) 4 ts set rxg set txg 4 ts 1 to 2 ts 6 ts sof id+com+data+crc eod ack bus int write ? it status register ? write ? last error register ? write ? last message register ? write ? message length and status register ? write ? message status ?
38 TSS463-AA 4205a ? auto ? 03/03 channel registers there is a total of 14 channel register sets, each occupying 8 bytes for addressing sim- plicity, integrated into the circuit. each set contains two 2 x 8-bit registers for the identifier tag, identifier mask and command fields plus two 1 x 8-bit registers for dma pointers and message status. the base_address of each set is: (0x10 + [0x08 * channel_number]) . when the tss463aa is reset either via the external reset pin or the general reset command, the channel registers are not affected. that is, on power-up of the circuit, all the channel registers start with random values. due to this fact, the user should take care to initialize all the channel registers before exiting from idle mode. the easiest way to disable a channel register is to set the received and transmitted bits to 1 in the message length and status register. table 8. channel register sets map table 9. channel register set structure channel number from to channel number from to 6 0x40 0x47 13 0x78 0x7f 5 0x38 0x3f 12 0x70 0x77 4 0x30 0x37 11 0x68 0x6f 3 0x28 0x2f 10 0x60 0x67 2 0x20 0x27 9 0x58 0x5f 1 0x18 0x1f 8 0x50 0x57 0 0x10 0x17 7 0x48 0x4f reg. name offset bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 id_mask 0x07 id_m [3:0] x x x x id_mask 0x06 id_m [11:4] (no register) 0x05 x x x x x x x x (no register) 0x04 x x x x x x x x mess_l/ sta 0x03 m_l [4:0] cher chtx chrx mess_ptr 0x02 drack m_p [6:0] id_tag/ cmd 0x01 id_t [3: 0] ext rak rnw rtr id_tag 0x00 id_t [11:4]
39 TSS463-AA 4205a ? auto ? 03/03 identifier tag and command registers the identifier tag and command registers are located at the base_address and base_address + 1. it allows the user to specify the full 12-bit identifier field of the iso standard and the 4-bit command. read/write registers. id_t [11:0]: identifier tag upon a reception hit (i.e, a good comparison between the identifier received and an identifier specified, taking the comparison mask into account, as well as a status and command indicating a message to be received), the identifier tag bits value will be rewritten with the identifier bits actually received. ext, rak, rnw and rtr (see section ? message types ? , page 45). no comparison will be done on the command bits, except on ext bit. the rak, rnw and rtr bits will be written into the first byte of the message upon a reception hit. the rnw and rtr bits, as well as the status bits in the length and status register, must be in a valid position for reception or transmission. if not, the message corresponding to this identifier is considered as inactive or invalid. the way of knowing if an acknowledge sequence was requested or not is to check the first byte of the message. message pointer register the message pointer register at address (base_address + 0x02) is 8 bits wide. it indi- cates where in the message data ram area the message buffer is located. read/write register. drak: disable rak (used in ? spy mode ? ) in reception: whatever is the rak bit of the incoming valid frame, no ack answer will be set. if the message was successfully received, an it is set (rok or rnok). in transmission: no action. one : disable active, ? spy mode ? . zero : disable inactive, normal operation. m_p [6:0]: message pointer since the message data ram area base address is 0x80, the value in this register is the offset from that address. if the message buffer length value is illegal (i.e. zero), this register is redefined as being a link pointer, thus containing the channel number of the channel that contains the actual message pointer, message length and received status. however, the identifier, mask, error and transmitted status used will be that of the origi- nally matched channel. in any case, if a link is intended, the three high bits of m_p [6:0] should be set to 0. 7 6 5 4 3 2 1 0 id_t 3 id_t 2 id_t 1 id_t 0 ext rak rnw rtr base_address + 0x01 7 6 5 4 3 2 1 0 id_t 11 id_t 10 id_t 9 id_t 8 id_t 7 id_t 6 id_t 5 id_t 4 base_address + 0x00 7 6 5 4 3 2 1 0 drak m_p 6 m_p 5 m_p 4 m_p 3 m_p 2 m_p 1 m_p 0 base_address + 0x02
40 TSS463-AA 4205a ? auto ? 03/03 this allows several channels to use the same actual reception buffer in message data ram, thus diminishing the memory usage. note: only 1 level of link is supported. message length and status register the message length and status register at address (base_address + 0x03) is also 8 bits wide. it indicates the length of reserved for the message in the message data ram area. read/write register. m_l [4:0]: message length the 5 high bits of this register allows the user to specify either the length of the message to be transmitted, or the maximum length of a message receivable in the pointed recep- tion buffer. note: the first byte in this register does not contain data, but the length of the message received. this implies that the length value has to be equal to or greater than the maxi- mum length of a message to be received in this buffer (or the length of a message to be transmitted) plus 1, thus allowing a maximum length of 30 bytes and a minimum length of 0 byte. if the value of this field is ? illegal ? (i.e 0x00) then this message pointer is defined as being a link (see message pointer and register and ? linked channels ? on page 53). note: different of a reply request frame with no in-frame reply (deferred reply). cher: channel error status and abort command as status, this bit is set by the tss463aa when error occurs in transmission or on a received frame. the user must reset it. to abort the transmission defined in the channel, this bit can be set to 1 by the user (see section ? activate, idle and sleep modes ? , page 52 and ? abort ? on page 50). chtx: channel transmitted and transmit enable command chrx: channel received and receive enable command the 2 low order bits of this register contain the message status. together with the rnw and rtr bits of the command register (base_address + 0x01), they define the message type of this channel (see section ? message types ? on page 45). as a general rule, the status bits are only set by the tss463aa, so the user must reset them to perform a 7 6 5 4 3 2 1 0 m_l 4 m_l 3 m_l 2 m_l 1 m_l 0 cher chtx chrx base_address + 0x03 m_l [4:0] = 0x00 linked channel m_l [4:0] = 0x01 frame with no data field (*) m_l [4:0] = 0x02 frame with 1 data byte - - - - - - - - - - - - - - - - - - - - - - - - - - - - - m_l [4:0] = 0x1d frame with 28 data bytes m_l [4:0] = 0x1e frame with 29 data bytes m_l [4:0] = 0x1f frame with 30 data bytes
41 TSS463-AA 4205a ? auto ? 03/03 transmission (chtx) or/and a reception (chrx). the received and transmitted bits are only set if the corresponding frame is without errors or if the retry count has been exceeded. identifier mask registers the identifier mask registers (base_address + 0x06 and base_address + 0x07) allow bitwise masking of the comparison between the identifier received and the identifier specified. read/write registers. id_m [11:0]: identifier mask a value of 1 indicates comparison enabled. a value of 0 indicates comparison disabled. example: ? id_m[11:0] = 0x0ff8 ? acceptance: id ? s from 0x0ff8 up to 0x0fff 7 6 5 4 3 2 1 0 id_m 3 id_m 2 id_m 1 id_m 0 x x x x base_address + 0x07 7 6 5 4 3 2 1 0 id_m 11 id_m 10 id_m 9 id_m 8 id_m 7 id_m 6 id_m 5 id_m 4 base_address + 0x06
42 TSS463-AA 4205a ? auto ? 03/03 mailbox the mailbox contains all the messages received or to be transmitted. each messages is link to a channel. the mailbox ram area has 128 bytes and is mapped from 0x80 to 0xff (see section ? mapping ? , page 26 ). the message (or message buffer) is composed of: 1 byte of message status (only used in receiving), n bytes of data. these data are the bytes of the data field of the frame with the same organization. the message is pointed by the message pointer register of the channel, the length of the message is given by the message length and status register of the channel. this area is a pure ram, it contains a random value after reset. figure 27. message buffer structure for reception cher chtx chrx message pointer register drak m_p [6..0] message length and status register m_l [4..0] rtr rnw rak m_l [4..0] = n+1 received received received received data 0 message rtr rnw id [11..0] ext sof data 0 data n fcs eod ack eof received data frame, immediate or deffered reply received data n received m_p + 0x80 + n + 2 ( m_l >= n + 2 ) m_p + 0x80 rak
43 TSS463-AA 4205a ? auto ? 03/03 figure 28. message buffer structure for transmission message status (pointed by: message pointer register) (no significant value in case of message to be transmitted) rrak: received rak bit this bit is the rak bit coming from the com field of the received frame. rrnw: received rnw bit this bit is the rnw bit coming from the com field of the received frame. rrtr: received rtr bit this bit is the rtr bit coming from the com field of the received frame. rm_l[4:0]: message length of the received frame if the data field of the received frame included data0 to datan, rm_l[4:0] = n+1, even if the reserved length (message length and status register) is larger. cher chtx chrx message pointer register drak m_p [6..0] message length & status register m_l [4..0] da ta 0 message rtr rnw rak id [11..0] ext sof data 0 data n fcs eod ack eof transmitted data frame transmitted data n transmitted m_p + 0x80 + n + 2 ( m_l >= n + 2 ) m_p + 0x80 (nothing) 7 6 5 4 3 2 1 0 rrak rrnw rrtr rm_l4 rm_l3 rm_l2 rm_l1 rm_l0
44 TSS463-AA 4205a ? auto ? 03/03 figure 29. message status updating message data (string pointed by: message pointer register + 1) data0 is the first received (or transmitted) byte, datan is the last one. note: 1. if the length reserved (in the message length and status register) for an incoming frame is 2 bytes greater or more, the tss463aa will write the 2 bytes of the crc field in the message string just after datan. because the van frame does not content a message length, the only way for the component to know the length of the data field is either the message length register value, either the eod field detection. when the reserved length is too large, at the moment when it detects the eod, the tss463aa has already written the 2 bytes of the crc field, considering these bytes as normal data. 2. the mailbox ram area is a circular buffer. the next location after 0xff is 0x80. data frame immediate reply i, p c frame type node x message status on node a after it(*) commu- node a rak rnw rtr length previous value i, c p rak rnw rtr deferred reply previous value i, c p rak rnw rtr data frame i, p c immediate reply i, c p rak rnw rtr length deferred reply i, c p rak rnw rtr length previous values p: producer i: initiator c: consumer (*) after it rok or rnok. in case of it re, the values can be erroneous. nication 7 6 5 4 3 2 1 0 datan - - - - - - - - - - - - - - - - - - -- - - - - - data0
45 TSS463-AA 4205a ? auto ? 03/03 message types there are 5 basic message types defined in the tss463aa. two of them (transmit and receive message types) correspond to the normal frame, and the rest correspond to the different versions of reply frames. to transmit a normal data frame on the van bus, the user must program an identifier as a transmit message. the tss463aa will then transmit this message on the bus until it has succeeded or the retry count is exceeded. the opposite of the transmit message type is the receive message type. this message type will not generate any frames on the bus. instead it will listen to the bus until a frame passes that matches its identifier, with the mask taken into account, and then receive the data in that frame. the data received will be stored in the message buffer and the length of the message received is stored in the first byte of the message buffer. the actual identifier received is stored in the identifier register itself. this identifier may differ from the identifier specified in the register due to the effect of the mask register. normally this should not interfere with the next identifier comparison since the bits that may differ are masked via the mask register. the reply request message type is a demand to transmit on the van bus a reply request. when this message type is programmed, three things can happen. in the first case no other modules on the bus responded with an in-frame reply, and in this case the tss463aa will set the message type to the after transmission state. when this message type is programmed, the tss463aa will listen on the bus for a deferred reply frame matching this identifier, without transmitting the reply request. transmit message rnw rtr chtx chrx initial setup 0 0 0 don ? t care after transmission 0 0 1 unchanged receive message rnw rtr chtx chrx initial setup 0 1 don ? t care 0 after transmission 0 1 unchanged 1 reply request message rnw rtr chtx chrx initial setup 1 1 0 0 after transmission (waiting for reply) 1 1 1 0 after reception (of reply) 1 1 1 1
46 TSS463-AA 4205a ? auto ? 03/03 the second case is that another module on the bus replies with an in-frame reply. in this case the message type will pass immediately into the after reception state, without pass- ing the after transmission state. in the third case the tss463aa has not yet started to transmit the reply request, when another module either requests a reply, and gets it, or transmits a deferred reply. warn- ing! this should be avoided as it may result in an illegal message type (illegal reply request). the immediate reply message will attempt to transmit an in-frame reply, using the data in the message buffer. above a deferred reply message is shown. this message type will immediately trans- mit a deferred reply frame. finally there is the reply request detector message type. its purpose is to receive a reply request frame and notify the processor, without transmitting an in-frame reply. the table above shows all inactive messages types. the last combination will transmit a reply request, but will not receive the reply since its buffer is tagged as occupied. reply request message without transmission rnw rtr chtx chrx initial setup 1 1 don ? t care 0 after reception 1 1 unchanged 1 immediate reply message rnw rtr chtx chrx initial setup 1 0 0 0 after transmission 1 0 1 1 deferred reply message rnw rtr chtx chrx initial setup 1 0 0 1 after reception (of reply request) 1 0 1 1 reply request detection message rnw rtr chtx chrx initial setup 1 0 1 0 after reception 1 0 1 1 inactive message rnw rtr chtx chrx recommended don ? t care don ? t care 1 1 after transmission 0 0 1 don ? t care after reception 0 1 don ? t care 1 illegal reply request 1 1 0 1
47 TSS463-AA 4205a ? auto ? 03/03 priority among the different channels the priority handling on the van bus itself is already explained in the line interface sec- tion. the priorities for the messages in the tss463aa is however slightly different. for instance, it ? s possible that an identifier matches two or more of the identifiers pro- grammed into the registers. in this case, it is the lowest identifier number that has priority. i.e., if both identifier 5 and 10 match the identifier received, it is the identifier 5 that will receive the message. however, since the identifier 5 will become an inactive message when it has received the frame, the next time the same identifier is seen on the bus, the corresponding data will be received by identifier 10. the same is valid for messages to be transmitted, i.e. if two or more messages are ready to be transmitted, it is the one with the lowest identifier number that will get priority. retries, rearbitrate and abort retries and rearbitrate commands are located, respectively, in the transmit control register and in the command register. an abort command is located in each channel register set, in the message length and status register (base_address + 0x03). these three commands are available only when the tss463aa is a producer. figure 30. transmit function activate ch. enabled in xmit mode ? no select the lowest ch. number and load ? max - retries ? yes abort activated on current ch. ? yes disable of current ch. no wait for bus free (eof+ifs= 12 timeslots) retry needed ? abort no no abort required rearbitrate? on current ch. rearbitrate yes transmit frame and wait for the end decrement retry counter
48 TSS463-AA 4205a ? auto ? 03/03 retries the purpose of the retries feature is to provide, for the user, the capability of retrying a transmit request in case of failure, when a node tries to reach another node, either on normal data frame or on reply request frame. the maximum number of retries is programmable through mr[3:0] of the transmit con- trol register (0x01). when a channel is enable ? bit chtx = 0 of message length and status register, a 4-bit counter is loaded with mr[3:0]. at each attempt, this counter will count-down to 0, an it te is set in the interrupt status register (0x09), and the trans- mission is stopped. mr[3:0] = 1 indicates 1 retry, hence 2 transmission attempts will be performed (see table 5, ? retries, ? on page 28). the number of retries performed, as well as the current channel number associated, can be read in the transmission status register (0x05). the last error status register (0x07) informs about the trouble uncounted: failure cases: ? code viol (cv error bit) ? acknowledge error (acke error bit) ? crc error (fcse error bit) it should be noticed that contention is considered as normal csma/cd protocol and, therefore, is not taken into account in failure cases. so, an 'infinite' number of attempts can be performed if bus contention occurs continuously. there is only one retry counter for all channels. when the user writes the max_retries value, all channels start their transmission with this parameter. rearbitrate the purpose of rearbitrate feature is to postpone a channel already in transmission in order to authorize an higher priority (see section "priority among the different chan- nels", page 47) message to be transmit. typical example max_retries = 1 (2 transmissions attempts). if ch8 is in a the retry loop and the user wants to transmit the ch5 without waiting the end of the loop, the user can use the rearbitrate command. the tss463aa will then wait until the end of the current transmission, reload the retries counter and enable the ch5 to transmit. at the end of this transmission ch5, either when the attempt is successful or the exceeded retry count is reached, the retries counter is reloaded and the transmission is activated for the ch8 again.
49 TSS463-AA 4205a ? auto ? 03/03 figure 31. rearbritrate example figure 32. idle and rearbitrate example if the user sets the idle bit anywhere (after rearbitrate), the idle mode is entered only at the end of all the transmit attemp ts (for more information about idle command, see ? activate, idle and sleep modes ? on page 52.). first attempt xmit ch5 ex: fcs error rearbitrate eof+ifs (activate ch5) delay set chtx/ch5 & it rok xmit ch8 (load max-retries) (load max-retries) * (not seen by application) (load max-retries) ex: fcs error (not seen by application) stand-by first attempt xmit ch8 second attempt xmit ch8 (retries - 1) delay set cher & chtx /ch8, ex: set fsce status bit and set it te delay v viol viol viol eof+ifs: 8 + 4 t imeslots delay viol: 12 timeslots * (not seen by application means no it generation) first attempt xmit ch5 ex: fcs error rearbitrate eof+ifs (activate ch5) set chtx/ch5 & it rok xmit ch8 (load max-retries) (load max-retries) (load max-retries) ex: fcs error (not seen by application) first attempt xmit ch8 second attempt xmit ch8 (retries - 1) idle command idle set cher & chtx /ch8, ex: set fsce status bit and set it te delay delay delay viol viol viol eof+ifs: 8 + 4 t imeslots delay viol: 12 timeslots * (not seen by application) * (not seen by application means no it generation)
50 TSS463-AA 4205a ? auto ? 03/03 figure 33. disable channel after rearbitrate in this case, the tss463aa completes the current attempt (ch8) and let the transmission go on the new channel (ch5 if validated), otherwise it stops all attempts on the current channel. abort an abort command is dedicated to channels already enabled in transmission or in in- frame response. for example, this command can be used to break the retry procedure on one channel. abort channel is done by setting the error bit (cher) in the message length and status register (base_address + 0x02). this command is taken into account if the channel aborted is not transmitted. when this abort command is really done, the tss463aa set to 1 the transmitted bit (chtx) of the message length and status register. the abort mechanism is integrated into the transmit function. this mainly means, abort, priority and retries live together in the transmit function. first attempt ex: fcs error rearbitrate (activate ch5) set chtx/ch5 & it tok set cher & chtx /ch5, xmit ch8 (load max-retries) (load max-retries) (not seen by application) ex: set acke status bit stand-by first attempt xmit ch5 second attempt xmit ch5 ex: ack error (not seen by application) (retries - 1) eof+ifs stand-by disable ch8(*) (*) the disable is applied setting the chtx/ch8 bit to 1. and set it te ko ok delay delay delay viol viol viol eof+ifs: 8 + 4 t imeslots delay viol: 12 timeslots
51 TSS463-AA 4205a ? auto ? 03/03 figure 34. abort example reset ch s initialization activate abort ch0 (before xmit) set chtx/ch0 abort ch13 (before xmit) abort ch4 (during xmit) set chtx/ch4 &it rok set chtx/ch6 & it rok if successful set chtx/ch6 & it rok if successful /ch6 & set chtx/ch13 xmit ch6 xmit ch6 xmit ch4 12 timeslots if previously failed xmit ch6 if previously failed it rok or it re set chtx or cher
52 TSS463-AA 4205a ? auto ? 03/03 activate, idle and sleep modes sleep, idle and activate commands are located in the command register (0x03). these three commands are general commands for the tss463aa. idle and activate commands after reset, the tss463aa starts in idle mode. in this mode, the oscillator operates (ckout pin active) but the circuit cannot transmit or receive anything on the van bus. the txd output (pin 12) is in tri-state mode, a pull-up resistor must be provided exter- nally or by the line driver to avoid floating state on the van bus. to activate the tss463aa, the user must set the activate bit (acti) and reset the idle bit (idle). figure 35. idle and activate timings in both cases, the idle state can be verified reading the line status register (0x04). sleep command if the user sets the sleep bit (sleep), the tss463aa enters in sleep mode, regardless of the values of activate and idle bits. it means that, all non-user registers are set-up to reduce the power consumption and the internal oscillator is immediately stopped. then, accesses to all registers (and to the messages) via the spi/sci interface are impossible and ckout is not provided. to exit from this mode the user must apply either an hardware reset (external reset pin) either an asynchronous software reset (via the spi/sci interface). in a typical application (see figure 5), using the ckout feature (pin 8), if the tss463aa is put in sleep mode, the clock provided to the microcontroller is stopped. so, the system does not run and the only way to awake this application is an external reset. (max) rxd txd after reset idle mode activate mode activate command 3 ts 8 ts 12 ts ts: timeslot period sof sof idle command fcs eod ack 5 ts 4 ts rxd int idle mode activate mode
53 TSS463-AA 4205a ? auto ? 03/03 linked channels the linkage feature allows two channels to share the same message area, the message pointer and the message length assumes this property: zero value as message length (m_l [4:0] - base_address + 0x03 ) declares the channel linked to another channel. the number of this other channel is defined in the message pointer field (m_p [6:0] - base_address + 0x02 ). the pointer and the length values for the message area are defined only once, in the register set of this other channel. only one level of linkage can be created. this means, (see figure 36) a channel k can be linked to the channel i but not to channel j, already defined as linked to channel i. all the others can be different between the two channels, for example the id_tag. figure 36. linkage mechanism this message area sharing permits either to optimize the allocation of the 128 bytes of data, or to perform some special communications between the different nodes of the network. id_tag j (msb) id_tag j (lsb) ext rak rnw rtr drak i 0x00 chrx message status data 0 --- channel i --- id_tag i (msb) id_tag i (lsb) ext rak rnw drak mess_ptr mess_len = n+2 cher chtx chrx id_mask i (lsb) --- channel j --- data n the channel j linked to the channel i . . . . length = n+2 --- message for channels i & j --- channel i and j share the same message area id_mask i (msb) rtr cher chtx id_mask j (msb) id_mask j (lsb)
54 TSS463-AA 4205a ? auto ? 03/03 electrical characteristics dc characteristics table 10. ta = -40 c to 125 c; v cc = 5v + 10%; v ss = 0v absolute maximum ratings ambient temperature under bias: automotive........................................................-40 c to 125 c storage temperature ........................................-65 c to 150 c voltage on v cc to v ss .......................................... -0.5 to +7.0v voltage on any pin to v ss ..........................-0.5v to v cc +0.5v *notice: stresses at or above those listed under absolute maximum ratings may cause permanent dam- age to the device. this is a stress rating only and functional operation of the device at these or any other conditions exceeding those indicated in the operational sections of this specification is not implied. exposure to absolute maximum rating conditions may affect device reliability. symbol parameter min. max unit test conditions v il input low voltage -0.5 0.3 v cc min v v ih input high voltage 0.7 v cc max v cc +0.5 v v hy hyteresis voltage of trigger cmos inputs 0.4 - v see table v ol output low voltage 0.4 v i ol = 3.2 ma, vcc min v oh output high voltage 2.4 v i oh = -3.2 ma, vcc min i l input leakage current (sclk, mosi, ss) 5 a 0 < v in < v cc i oz output tristate leakage current (miso) 5 a 0 < v in < v cc r pu, r pd input pull-up and pull- down resistors 70 k ? note 4 c io i/o buffer capacitance 10 pf not tested i ccsb power supply current sleep mode 50 a (note 1) i ccop power supply current idle or active mode 9 ma (notes 2, 3) notes: 1. sleep mode i ccsb is measured according to a v ss clock signal. 2. active mode i ccop is measured at: xtal = 8 mhz clock, van speed rate = 125 kts/s. 3. i cc is a function of the clock frequency. figure 38 displays a graph showing i cc versus clock frequency. 4. reset , rxd0, rxd1, rxd2 inputs.
55 TSS463-AA 4205a ? auto ? 03/03 figure 37. i cc figure 38. i ccop versus clock frequency at 125 ktimeslot/s ma 9 24 mhz 8.5 8 7.5 68
56 TSS463-AA 4205a ? auto ? 03/03 ac characteristics t a = -40 c to 125 c; v cc = 5v + 10%; v ss = 0v table 11. microprocessor interface c load = 200pf on spi/sci lines note: 1. simulated data symbol characteristic min max unit f op operating frequency spi sci dc dc 4 125 mhz khz t cyc cycle time spi sci 250 8 - - ns ms t lead enable lead time 4 - xtal period t lag enable lead time 12 - xtal period t w(sckh) clock (sclk) high time 100 - ns t w(sckl) clock (sclk) low time 100 - ns t su data setup time (inputs) 40 - ns t h data hold time (inputs) 40 - ns t a slave access time (time to data active from high-impedance state) 0 100 ns t dis slave disable time (hold time to high- impedance state) - 200 ns t v data valid (after enable edge) - 60 ns t ho data hold time (outputs after enable edge) 0 - ns t izil (1) int float pulse width 20 ns a ss (input) miso (output) mosi (input) sclk (input) int float pulse only when address is 0x08 to 0x0b izil t cyc t lead t w(sckl) t w(sckh) t flag dis t ho t v t h su t t izil t t
57 TSS463-AA 4205a ? auto ? 03/03 interface oscillator characteristics figure 39. c2 versus frequency note: c1 (no capacitance needed) see figure 5 . external clock drive characteristics (xtal1) 200 100 33 12 4 8 mhz pf symbol parameter min max unit t chch oscillator period 120 ns t chcx high time 20 ns t clcx low time 20 ns t clch rise time 20 ns t chcl fall time 20 ns t chcx t clcx t chch xtal1 v ih v il t clch t chcl v ih v ih v il
58 TSS463-AA 4205a ? auto ? 03/03 packaging information so16 so mm inch a 2.35 2.65 0.093 0.104 a1 0.10 0.30 0.004 0.012 b 0.35 0.49 0.014 0.019 c 0.23 0.32 0.009 0.013 d 10.10 10.50 0.398 0.413 e 7.40 7.60 0.291 0.299 e 1.27 bsc 0.050 bsc h 10.00 10.65 0.394 0.419 h 0.25 0.75 0.010 0.029 l 0.40 1.27 0.016 0.050 n 16 16 a 0 8 0 8
59 TSS463-AA 4205a ? auto ? 03/03 ordering information part number supply voltage temperature range package packing TSS463-AA 5v + 10% -40 c to +125 c so16 stick TSS463-AA: r 5v + 10% -40 c to +125 c so16 tape and reel
printed on recycled paper. ? atmel corporation 2003. all rights reserved. atmel, the atmel logo, and combinations thereof are registered trademarks of atmel corporation or its subsidiaries. other terms and product names in this document may be the trademarks of others. ? atmel corporation 2003. atmel corporation makes no warranty for the use of its products, other than those expressly contained in the company ? s standard warranty which is detailed in atmel ? s terms and conditions located on the company ? s web site. the company assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without n otice, and does not make any commitment to update the information contained herein. no licenses to patents or other intellectual property of at mel are granted by the company in connection with the sale of atmel products, expressly or by implication. atmel ? s products are not authorized for use as critical components in life support devices or systems. atmel headquarters atmel operations corporate headquarters 2325 orchard parkway san jose, ca 95131 tel 1(408) 441-0311 fax 1(408) 487-2600 europe atmel sarl route des arsenaux 41 case postale 80 ch-1705 fribourg switzerland tel (41) 26-426-5555 fax (41) 26-426-5500 asia room 1219 chinachem golden plaza 77 mody road tsimhatsui east kowloon hong kong tel (852) 2721-9778 fax (852) 2722-1369 japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel (81) 3-3523-3551 fax (81) 3-3523-7581 memory 2325 orchard parkway san jose, ca 95131 tel 1(408) 441-0311 fax 1(408) 436-4314 microcontrollers 2325 orchard parkway san jose, ca 95131 tel 1(408) 441-0311 fax 1(408) 436-4314 la chantrerie bp 70602 44306 nantes cedex 3, france tel (33) 2-40-18-18-18 fax (33) 2-40-18-19-60 asic/assp/smart cards zone industrielle 13106 rousset cedex, france tel (33) 4-42-53-60-00 fax (33) 4-42-53-60-01 1150 east cheyenne mtn. blvd. colorado springs, co 80906 tel 1(719) 576-3300 fax 1(719) 540-1759 scottish enterprise technology park maxwell building east kilbride g75 0qr, scotland tel (44) 1355-803-000 fax (44) 1355-242-743 rf/automotive theresienstrasse 2 postfach 3535 74025 heilbronn, germany tel (49) 71-31-67-0 fax (49) 71-31-67-2340 1150 east cheyenne mtn. blvd. colorado springs, co 80906 tel 1(719) 576-3300 fax 1(719) 540-1759 biometrics/imaging/hi-rel mpu/ high speed converters/rf datacom avenue de rochepleine bp 123 38521 saint-egreve cedex, france tel (33) 4-76-58-30-00 fax (33) 4-76-58-34-80 e-mail literature@atmel.com web site http://www.atmel.com 4205a ? auto ? 03/03 /xm

▲Up To Search▲

Price & Availability of TSS463-AA

	To Download TSS463-AA Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .